Hello Experts, Having an intermittant issue with sending mail from an Exchange 2010 server. When a message is sent the message-ID contains the FQDN and other times it doesn't. I can't seem to figure out why this changes. For example I send a message and I will send this Message-ID with our FQDN "Message-ID: <A5C9F5F9-D4E1-DF11-9C32-0019B941DFDA@mail.mycompany.com>", other times I will just send the message-ID "Message-ID: <A5C9F5F9-D4E1-DF11-9C32-0019B941DFDA>". We are not using any smart host or spam filter other than Forefront. My send connectors all have the FQDN entered. This was never a problem until one of our customers, who uses Postini, enabled this for added security. Since they are our customers the burden pretty much falls on us. The rejection error is this "Postini #553 5.0.0 Message-Id header line format error ##" and we have verified that the Message-ID w/o the FQDN is the issue. Any ideas?

On Tue, 2 Nov 2010 15:04:17 +0000, Always a Fight wrote: >Hello Experts, Having an intermittant issue with sending mail from an Exchange 2010 server. When a message is sent the message-ID contains the FQDN and other times it doesn't. I can't seem to figure out why this changes. For example I send a message and I will send this Message-ID with our FQDN "Message-ID: <A5C9F5F9-D4E1-DF11-9C32-0019B941DFDA@mail.mycompany.com>", other times I will just send the message-ID "Message-ID: <A5C9F5F9-D4E1-DF11-9C32-0019B941DFDA>". We are not using any smart host or spam filter other than Forefront. My send connectors all have the FQDN entered. This was never a problem until one of our customers, who uses Postini, enabled this for added security. Since they are our customers the burden pretty much falls on us. The rejection error is this "Postini #553 5.0.0 Message-Id header line format error ##" and we have verified that the Message-ID w/o the FQDN is the issue. Any ideas? From where are the messages with the malformed Messaged-ID data originating? If the message arrives at the Exchange server without a Message-ID header Exchange will add one (as all MTAs should). But if the Message-ID header is present there's no validation performed on its contents since it's the job of the MUA (or the MTA that accepts the message from the MUA) to supply a correctly formatted set of headers and values. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

You nailed it with where it was originating. It seemed more random than what it really was but they were replying and forwarding messages that had the malformed Message-ID. Thanks for your help.

Well, I take this back. Although this seem to match what I was seeing we again ran into it even though the originating message was formed correctly. Turns out Microsoft CRM Dynamics removes the FQDN when you track it in Outlook. Why? no clue yet. I don't use CRM so in all my tests this is why I was unable to reproduce the problem. Any ideas on why CRM would remove the FQDN from the Message-ID?

On Wed, 3 Nov 2010 16:40:20 +0000, Always a Fight wrote: > > >Well, I take this back. Although this seem to match what I was seeing we again ran into it even though the originating message was formed correctly. > >Turns out Microsoft CRM Dynamics removes the FQDN when you track it in Outlook. Why? no clue yet. I don't use CRM so in all my tests this is why I was unable to reproduce the problem. > >Any ideas on why CRM would remove the FQDN from the Message-ID? The <domain> part of the message-id wasn't removed, it was never there. The message-id must be unique for every message. If they're redirecting the message they shouldn't be messing with the message-id header value. If they're forwarding the message then it's a new message and it should have a unique message-id. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I can say with certainty that the original message has the FQDN in the Message-ID and I can forward and reply to it and still keep the FQDN in the Message-ID. But when I turn on CRM tracking within Outlook and then forward or reply the FQDN is removed.

On Thu, 4 Nov 2010 15:33:59 +0000, Always a Fight wrote: >I can say with certainty that the original message has the FQDN in the Message-ID and I can forward and reply to it and still keep the FQDN in the Message-ID. If you reply to a message from "@serverA" the Message-ID header should have "@yourserver" in the outgoing headers, not the original message-id. Keep in mind that the message-id is useful only to the sender. Outside the originating system the data it contains is meaningless. All that matters to the receiving system is that it's correctly formatted. >But when I turn on CRM tracking within Outlook and then forward or reply the FQDN is removed. If the add-on software is providing the Message-ID it's doing it incorrectly. You'll have to take that up with the folks that provide the add-on stuff. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP